propagate registry object to material creation #46
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This prevented pyg4ometry from (in-)correctly validating material name duplicates. Also fix the duplicates, so that pyg4ometry can read back generated GDML files.
also see g4edge/pyg4ometry#195 for background
important note: while pyg4ometry could not read the generated files, Geant4 alsways could without problems. So this bug did never impact actual simulation runs, only people trying to read data from the GDML file.